Fixed your comment, @antonpirker.

Also, I know we had discussed maybe changing our internal imports of Event to import from types instead of _types; however, it looks like we would need to update many files manually to make this change.

Perhaps, it would make sense just to change the import in api, since that file is likely the one that external users would interact with the most anyway?

Its not as important right now do update our internal imports. We can do this in a later PR, with this PR we have everything in place that the users care about. Baby steps to success :-)

@antonpirker, yes of course, I was planning to make any import changes within a separate PR :)

What version is it available in?

@mdczaplicki This PR is not released yet. It should be included in our next release!

I see. When do you plan to release?

@mdczaplicki, there is no date set yet for the next release. However, we will probably release a new version including these changes sometime this week.

Would you say that 1.42 should be yanked? If we use dict[str, Any] for type hints then mypy is screaming that types are not matching. If we however use Event or Hint from sentry_sdk._types then test suite screams that those cannot be imported.

@mdczaplicki Apologies for the inconvenience. We plan to release a new version including these changes later today.

However, we will not yank 1.42 because the code itself remains backwards compatible. If you are encountering problems with the new type hinting, we would recommend updating your mypy configuration (e.g. you could import Event from sentry_sdk._types with a # type: ignore comment), or ideally updating to this new version once it is released later today.

Shouldn't you add the following to the file also? Otherwise non-typechecking environment can't do the import

else:
  Event = dict[str, Any]
  Hint = ...

and would instead need to do it ourselves

# my_project/module/types.py

if TYPE_CHECKING:
  from sentry_sdk.types import Event
else:
  Event = dict[str, Any]